home *** CD-ROM | disk | FTP | other *** search
- Path: web.cae.ca!usenet
- From: fraserh@cae.ca (Fraser Hutchinson)
- Newsgroups: comp.lang.c++
- Subject: Re: Borland 4.5 application won't work on its own
- Date: 18 Mar 1996 19:26:16 GMT
- Organization: CAE Electronics Ltd.
- Message-ID: <4ikdco$rck@web.cae.ca>
- References: <4i3fhh$bor@dole.uninett.no>
- NNTP-Posting-Host: pch63.cae.ca
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=US-ASCII
- X-Newsreader: WinVN 0.99.7
-
- In article <4i3fhh$bor@dole.uninett.no>, Kristoffer.Moe@nifu.no says...
- >
- >I have recently developed an application with Borland C++
- >4.5 and OWL. It is based on a TDecoratedFrame parent with a TDialog as a
- >child. The program works nicely (acceptably that is) when compiled and run
- >'within' Borland IDE. However, when it is started on its own, whithout the
- >Borland IDE loaded in the machine at all, it displays the TDecoratedFrame,
- >and generates a General Protecton Fault. With Winspector running in the
- >background it works again. The application is based on AppExpert.
-
- I have seen this a lot with IDE's: my guess here is that you have a Rogue
- pointer that is corrupting a memory address that doesn't bother the IDE but
- crashes Windows. NULL pointer assignment errors have caused this. I would
- suggest running the app through a memory leak detector like Purify or Bounds
- Checker.
-
- Fraser
-
-
-